home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
wildcat
/
vm100a_b.zip
/
VMFILES.DAT
/
INSTALL.DOC
< prev
next >
Wrap
Text File
|
1996-05-06
|
32KB
|
686 lines
┌───────────────────────────────────────────────────────────────────────────┐
│ Beta Release Program Installation Notes ViaMAIL! v1.00a │
└───────────────────────────────────────────────────────────────────────────┘
If you haven't already read the contents of the README.1ST file, please
take a moment to do so now.
INTRODUCTION
Okay, getting this far you should be aware that this file contains the
only source of tangible documentation with regards to installing and
running ViaMAIL!. You're aware that we're busy working on getting the
online F1 help and normal documentation written. With that little
reminder I think we're ready to proceed.
INITIAL INSTALL
To install ViaMAIL! from the distribution archive, please use the
following steps:
1) Create a temporary work directory similar to below:
C:\TEMP
You can call it anything you wish however.
2) Unzip the contents of the distribution archive into that
directory.
3) From that directory run VMINSTAL.EXE.
4) Once VMINSTAL is finished, you may delete the files in the
work directory (created in step #1) and remove the directory.
5) Copy in your VM.ID file into the \VM10 directory. You did
download a key aready right? If not, be sure to pick one up
first.
WILDCAT! ENVIRONMENT VARIABLES
ViaMAIL! can make use of ALL the environment variables that WILDCAT!
uses to control/override the MDM file. However, in order for ViaMAIL!
to use the modem, it must use the modem definition file from it's own
internal database. THIS IMPORTANT TO UNDERSTAND. You may import your
existing MDM files from the \WILDCAT\MODEM\ directory into ViaMAIL! but
more on that in a bit.
LINE VERSES NODE
One of the things that has always been confusing to the novice SysOp
is the term nodes in fido as compared to the nodes in WILDCAT!. Adding
a mailer to that picture only serves to confuse the issue more. So in
an effort to reduce this, each of the individual PCs (or tasks) that
allows an incoming call (or local logon) is referred to as a LINE.
The current line number is always displayed in the top LH corner of the
screen and represents the WILDCAT! NodeID that will be used when the
call is passed to the BBS.
BATCH FILES
ViaMAIL! has been designed to operate from a single batch file which it
will create for you should one not exist and we highly recommend using
it. This is because the basic 'framework' of the batch file created by
ViaMAIL! is one which will automatically allow callers to the BBS as
well as one that will work with processing newly recieved mail/files.
Once you have a better understanding of how/what and why ViaMAIL! does
what it does, should then then consider adding in the additional
information your present setup dictates.
The line naming convention also applies to the batch files that run
ViaMAIL!, each line has it's LINEx.BAT file (where x = NodeID). So if
you set the WILDCAT! enviroment WCNODEID=2, then the line number would
be 2 and the batch file would be called LINE2.BAT.
It important to note that we highly discourage the use of 'common' batch
files using the DOS % variables to pass parameters. This is due to the
fact that certain lines can be configured to drop with certain error
levels to perform a function, but while those same errorlevels may
exist for another line, it may be configured to perform some other
function. Once you start using ViaMAIL!, you'll understand this a bit
more.
Please note, this is simply a recommendation, if you thoroughly
understand batch files, ViaMAIL! is flexible enough to allow you to do
that. Just take a moment to understand how ViaMAIL! works first before
proceeding off in that direction.
INSTALLATION
Now that we've given you a basis for the new product, following is a set
of steps that you should follow carefully.
1) Check your CONFIG.SYS file, if your have your FILES= line to
something less than 100, set it to 150 or more and reboot
if necessary.
2) From the DOS prompt type SET followed by pressing return. Among
other things, this should display a list of various environment
variables. If you have one specified called WCPORTID, type the
following command:
WCPORTID=
After entering this command, make sure to hit return. This will
remove the environment variable all together.
3) If you're currently using .MDM files from WILDCAT! and they PHYSICALLY
exist in the \WILDCAT\MODEM\ directory, you may skip this step all
together and proceed to step #4.
If you are using the default values stored in MAKEWILD, you'll need
to save them to a MDM file. Following are the steps required to
create the MDM file.
a) From the WILDCAT home directory, run MAKEWILD and select Modem
Settings.
b) At the bottom of the current window you notice there is a F4
button to save, press F4.
c) Think of a DOS file name to save it as, in this example lets
call it MYMODEM.MDM. Enter that file name making sure the path
reflects that of the \WILDCAT\MODEM\ directory (if you've named
\WILDCAT\ as something else, use that instead) The key here is
that the file must exist in a subdirectory off of WILDCAT!'s
home directory called \MODEM\.
d) Once the name has been entered, press F10.
e) Exit MAKEWILD and return to the \VM10 directory.
4) From the \VM10 directory type:
VM
This should bring ViaMAIL! up in local mode only (the modem should
not be active).
4) The screen that comes up is referred to as the 'Waiting for Calls'
screen. From this screen, press Alt-O. This should display a pull
down menu.
5) From the 'Setup' menu, highlight Mailer Options and press return.
Scroll down to mid screen, right hand side and enter in the
WILDCAT! home path. Once complete, press ESC one time.
6) Highlight the menu option 'Modem Configuration' and press return.
From here you should see the 'DEFAULT' modem definition. Press the
F5 key to import the MDM files (from WILDCAT!) into ViaMAIL!. Once
complete, you'll see a list of MDM files that now exist inside of
ViaMAIL!.
Note that the right hand column reflects the original DOS file name.
This name it what's used to tell ViaMAIL! which MDM file should be
used. Scroll through the items listed and find the MDM file that
you are using. If you don't find it, you may need to start over at
step #3.
7) Press ESC one time. This should return you to the 'Setup' menu.
From here select 'Line Batch Files' followed by pressing return.
The highlight bar should now be positioned on the current line
number. Normally this is 1, but if you've set the WCNODEID= to
something else, use that instead.
Press return and say Y to the prompt to create the batch file.
8) From here ViaMAIL! has just created a batch file in the \VM10
directory with the appropriate line number. If the NodeID was 1,
the batch file is called LINE1.BAT. Scroll down the batch file and
find the line that is similar to:
vm /n1 /e
What you're going to do is add the DOS file name of the MDM file to
use. So if your MDM file was called MYMODEM.MDM, you would change
the line to read:
vm /n1 /e /dmymodem
Once the changes are complete, press F10 to save it. This should
return you to the list of the line batch files, press ESC one time
to return to the menu. From here press ESC several times and when
prompted to return to DOS, do so.
9) Now here's the fun step, bringing up ViaMAIL! for the first time
with your modem live. From the \VM10 directory execute the
LINEx.BAT file that you edited in step #8.
Under normal circumstances, ViaMAIL! should have initialized the
modem and should now say (mid-screen) 'Waiting for Calls'. If it
doesn't, then you should probably try the above steps again to
verify you've entered everything correctly and the that MDM file is
actually in VM's database. If it still doesn't work, better give a
call to tech support.
10) Okay, from this point forward, ViaMAIL! is now ready to accept
incoming calls. If you don't want to be interrupted during the
remaining of the configuration, you should press Alt-O, under
'Setup', select Mailer Options and change the option called
'Take Modem Off-Hook in Menu: Y'
This will prevent ViaMAIL! from forcefully exiting the screens and
answering the call.
11) Press Alt-O and under 'SetUp', select System Addresses. This
presents you with a screen whereby you can enter in all your AKA
addresses (including your primary). Press INS and add the address
followed by pressing F10 to save it.
For those of you that are getting your mail from Panet Connect,
you'll notice that 1:3615/51 is already there and that the
option:
'Use w/EMSI handshake: N'
is set to N. This is necessary in order to properly transfer mail
with Planet Connect while at the same time permit the ViaTOSS! to
process PKTs from that address. More on ViaTOSS! later.
Once all the addresses are added, press ESC to return to the menu.
12) Select Packers/Unpackers. From this screen you will be presented
with a list of all the different compression types. You should edit
each one of these making sure the DOS paths are correct. Once those
changes are complete press ESC to return to the menu.
13) Select Mailer Options and enter in the correct drive letters for the
various paths. If you're a member of Fidonet, you should copy your
your current NODELIST.nnn file into the C:\VM10\NODELIST\
directory. We'll compile it in a bit.
If you're running a multi-line setup, you should make sure you
change the field 'Network/multi-line mode' to the appropriate type.
Pressing the SPACEBAR or F2 allows you to change it.
Most all of the default values should be left the way they are, you
can experiment with them later. You should take a moment however
to familiarize yourself with the remaining options on this screen.
Once complete, press ESC to return to the menu.
14) Select Mail Tosser Options and under the field 'Netmail Conference',
pressing F2 pulls up a list of WILDCAT! conferences and you should
select the appropriate one. Verify the various DOS paths and change
them to the appropriate drive letters. Again, take a peek at the
remaining options, but leave them at the default values for now.
Press ESC to return to the menu.
15) Select File Tosser options and as with step #14, set the drive
letters and then press ESC to return to the menu.
16) Select Response Messages. This screen presents you with a list of
all the prompts that ViaMAIL! in some form or another will present
to your callers or send back to them in automated response
messages. You may edit all of these as necessary at a later time,
but for now you should select msg #1 - Introduction screen followed
by pressing return.
This is the 'prelog' screen that gets displayed to your callers
immediately upon modem carrier being detected. You should change
this as need be pressing F10 to save. Once changes are complete,
press ESC to return to the previous screen.
Selecting msg #36 is a complete set of help information necessary
for your downlinks to use the new AREAFIX/RAID functionality of
ViaMAIL!. By the way, this has been renamed to ECHOSERV and ARCSERV
respectively. You should read this message over to become familiar
with it. This same information is available in a file called
VIASERV.DOC.
Once your processing is complete, press ESC to return to the menu.
17) Select Phone Translations. This option allows you to specify
number translation as well as costing values. The functionality of
this is very similiar to FrontDoor/IM. Press ESC to retun to the
menu.
18) Select Post Call Commands. Nothing needs to be done here except to
point out that ViaMAIL! has the ability to execute the commands
entered here after every MAIL call that comes in. However,
depending on setting under Mailer Options:
'Execute PC cmds after mail:'
it might be limited to an event. Either way, the series of commands
entered here will be performed (based upon line selection) and is
useful should you receive certain files and want them moved or
processed in some way. The default setup comes with commands to
move NODELIST and NODEDIFF files should they come in and well as
uncompress the ALLTICS.nnn file that comes down from Planet Connect.
As you can see, with a little imagination, you can do quite a bit
here. Once your 'dreaming' is complete, press ESC to return to the
menu.
19) Using the right arrow key, move over to the menu option 'Config'.
Select Network Management. Presented here are two networks that you
should use as a guide. FIDONET is a good case where you define the
the NODELIST, NODEDIFF, and various .NA/.NO files that are
associated with this network.
Inside of ViaMAIL!, everything is based upon networks, so if you
don't have the proper information defined here, then the nodelist
won't be compiled right (one nodelist per network), the echolist
and filelist areas will not be imported in the their respective
'Master Lists' and so on.
Spend a little time here and look around, I think you'll find it
refreshing that there is a bit of organization now to your needs.
You shouldn't modify anything here (yet), for now just look it over.
Once you're finished with looking at WSNET and FIDONET, press ESC to
return to the menu.
20) Select Node Management. This screen should remind you of how
WILDMAIL! is setup and is where you define each of your downlink
systems (NEVER your addresses). The most notable exceptions are:
Mail session pswd : Self-explanitory
ViaSERV! password : AREAFIX/RAID password from Subject line
Lines to dial node: When dialing this system, which lines of
ViaMAIL! can dial out to this node address
Subscribed confs : Simple name change, used to be 'Selected'
Of course there's a bit more with the ARCSERV (RAID) options, but
it's fairly straight forward. Once your viewing is complete, press
ESC to return to the menu.
21) The menu options Conference and File Area Management are virtually
identical to those found in WILDMAIL!. You should peruse these and
become familiar with the various options.
22) The Master Conference List and Master File Area List options are
also identical to WILDMAIL!'s Master List. The big difference is
that there is now a Master File Area List. Other than that, they
have the same use which is basically to provide you with a list of
conferences (for a given network) that you may add to your
configuration.
If the area is not in the master list, then you won't be able to
add it to your config. The only way to add areas to the Master list
is to either do it manually or import them from the defined
echo/filelists (defined under Network Management for the
appropriate network).
In ViaMAIL!'s present state, there should only be conf/file areas
from WSNET, we'll import the areas from Fido net in a bit.
You should peruse these two options and have a look at them. Once
your finished, press ESC to return to the menu.
23) Okay, we should be at the 'Config' menu now, if not, get there.
Select Magic File Definitions. This screen contain several sample
definitions of each type. The setup of this is quite simple.
You'll notice that the main difference between the Single File and
Magic Name types are where the DOS file name is placed.
In the Single File type, the file name is placed in the 'Definition
name' field and the path to that file in the 'DOS directory' field.
Whereas the Magic Name type use put the magic name in the
'Definition name' field and out the complete DOS file spec including
the file name in the 'DOS directory' field.
Press ESC to return the menu.
24) The remainder of the options on the 'Config' menu are pretty
straight forward with the exception to the Hatch Definitions.
Basically this option allow you to attach a name to a specific a
'file-spec' to hatch which can be either manually hatched or
executed via an event whereby you can specify up to 10 definitions
to be hatched.
Press ESC to return to the menu.
25) Using the right arrow key, select the 'Events' menu. Events in
ViaMAIL! are probably quite a bit different than your used to, but I
think you'll find them easier to use once you get the hang of them.
Basically there are 6 event types:
General Events (Mail)
Poll Node Events
Internal Events
External Events
Message Events
Hatch Events
General Events -
There are two types of mail events. One that runs on all the lines
which can effect the contents of the queue, meaning it can change
the hold status, etc. The second only affects a nodes call handling
options. Items such as answering the phone, permitting FREQs etc can
be performed but NO changes will be made to the messages in the
queue. Messages can still be sent (if permitted), but their status
can not be changed, this is why you can't select the option 'Schedule'.
Several new options has been added such as disabling the answering of
incoming calls and disabling the ability to make outbound calls.
Depending on the call type (via the 'All Lines/One Line Only' option)
dictates the scope of those commands.
If you've disabled the answering of incoming calls, when a call comes
in, you'll see a message appear at the bottom of the screen 'Phone
ringing...' for aprox 1/2 second then disappears allowing you to
continue making changes etc. This is done to let you know a call is
coming in (it's not going to be answered, but at least you know).
Routing of Mail
For those of you familiar with the way FD and IM handle the 'setup'
of routing, if you look closely, you see a similar setup in ViaMAIL!
The main difference is that it's menu driven. Each 'schedule' has
routing type commands that are associated with it that affect the
processing of mail. You attach a 'schedule' to a mail event and
when you run that event, the mail will get processed according to
the commands from the schedule.
Changing the schedule (or changing the event with a different
schedule) will change the behavior of how mail is processed. This
section on mail delivery is fairly complex and requires a few
examples to throughly explain it. But suffice to say, if you
understand the functionality of the commands from FD/IM, the same
rules apply here.
Please bear with us here and know that we'll cover this section
quite extensively in the upcoming documentation.
Poll Node Events -
You can specify a single poll event that creates poll entries into the
queue for up to 10 different node addresses.
Internal Events -
The internal events are things such as trimming the log files,
resetting the quick stats etc. These are 'run-once' type events as
compared to mail which could run for hours. There are two types of
internal events.
Multi line
Single line
Multi line only affects the log trimming events. If you select the
line(s) to run this event, then EACH LINE will run it's log trimmer
at the specified time. This saves you from having to enter 5 events
for five different lines.
Now the single line event is just that, no matter how many lines are
selected to run it, the first one that gets to it will be the one
that runs it and the others will simply log the 'missed attempt' and
determine the next event accordingly.
External Events -
These events are the most commonly used ones and work exactly the
same as the Multi line mode of the Internal Events. So if you want
all lines to drop at the specified time with the given errorlevel,
then you would select all those lines. Of course you'll need to have
a specific IF ERRORLEVEL statement in your batch file. Speaking of
which, while editing an exgernal event, pressing [F9] allows you to
edit the appropriate lines batch files as needed.
Message Events -
This event type allows you to send a message to a groups of nodes which
may contain up to 5 files attachments and also allows you to specify a
text file that should be imported into the message body.
Hatch Events -
This type allows you to select up to 10 hatch definitions (defined
under Hatch Management (see step #24) to be hatched at a given time.
This might be useful should you wish to hatch NODEDIFF files to your
downlinks on a weekly basis.
Multi-Time Selectability -
On all event types except mail, you may now specify up to 96 times
within a 24 hour period that the event should execute on. This is
done in 15 minute increments and and is toggled on by highlighting the
appropriate time and tapping the [SPACEBAR]. This should greatly
simplify your configuration time.
Event Disabling -
CAUTION - If you're anything like me, you'll forget to toggle the
'Active definition' field to Y and then the event won't run. It's
intentionally designed this way for the non-mail type events. This
is because those types of events force a specific action to take
place. So you're required to toggle this option to Y before it will
run.
Manually Executing Events -
With the individual event types, each has it's own screen designed to
categorize the event type. However, when manually executing an event,
you will be presented with a list of ALL the event types configured.
Simply select the approriate one and run it.
Okay, now that you're impressed with all the event types, it's time to
move on. <g>... Press ESC to return to the 'Events' menu.
26) Using the right arrow key, select menu 'Queues'. As you can see,
ViaMAIL! breaks up your netmail, TICS and outbound bundles for your
perusal. Each media type has it's own database of traffic. You
have an In/Outbound Netmail, In/Outbound TICs and finally the
actual Outbound Queue.
Outbound Queue -
To force a rebuild of outbound mail, from the Waiting for Calls
screen, simply press Alt-R. This will requalify all inbound and
outbound traffic and create the appropriate entries in this database.
Now under the 'Status' column, you will see up to 9 possible values
three of which I'll discuss. The others are self explanitory.
Priority - This indicates that the mail is urgent and will cause
VM to immediately dial out. Any mail having a lower
priority (Crash or Ready) will NOT be processed until
all mail of this type has been sent.
Crash - This functions identically to Priority, except all
mail with this status will be sent before sending
'Ready' status mail (Priority is done first of course).
Ready - This is the lowest priority of mail to go out. Both
Priority and Crash mail will be sent before this.
If you would like to change the status of any of the entries, you may
do so my pressing [F2]. [F3] allows you to reset the dial attempts
and [F4] allows you to change the destination system.
ViaMAIL! now supports a 'round-robin' method of sending outbound
mail. Observing the above rules, ViaMAIL! will determine the next
node to dial based upon the lowest number of attempts made. You can
also view a list of the associated outbound traffic by highlighting
the desired entry followed by pressing [ENTER].
In/Outbound Netmail -
This is pretty much self-explanitory.
In/Outbound TICs -
Inside of ViaMAIL!, you no longer store TIC files in their native
state. Instead, ViaMAIL! will import them into the inbound queue
where they will be processed by ViaTOSS!. Once processed, the
forwarded TICs (if there are any) will be placed in the Outbound
TICs queue and stored until transmission. Only at the point of
transmission will they become a physical file on your system.
The reasoning for this method is simple, it significantly reduces
the number of files on your hard drive, provides greater readbility
to know what TIC goes with what companion file and who's getting what.
The during the 'Pack Queue' event (Internal), the tics will be
purged from the database and their associated files will also be
'cleaned up' from disk. By the way, ViaMAIL! comes preconfigured to
run this event once a night. You should always peack the queue on
some sort of regular schedule otherwise the transmitted TICs and
their companion files will never be deleted.
Pressing ESC returns to the menu.
27) Select Pending xSERV Commands. This option is simply a temporary
database designed to hold ECHO/ARCSERV commands that are meant to be
processed offline. The only commands that should stay for any
amount of time are the GET RESCAN type commands. This is because
ViaTOSS! is the only program that will process these mainly because
this has to do with rescanning messages, something the tosser
normally handles anyway.
Press ESC to return to the menu.
28) The menu 'Global' contains various selection to globbaly modify, add
and delete conferences and File Areas. You'll use this more once
you start configuring your setup.
29) The menu option 'Misc' is a collection of some of the internal
events that you can run manually without having to run them as an
event. Sort of a short cut if you will.
As part of our initial setup, you should select 'Compile Nodelist'
followed by pressing F10 to go. If you're a member of Fidonet you
should have already copied the current NODELIST.nnn into the
\VM10\NODELIST\ directory (see step #13). ViaMAIL! will now
compile the nodelists from the two networks defined.
Once the process is complete, return to the menu and select 'Import
Echolists' and press F10 to go. This will import the echolist files
into the Masterlist.
30) Now that we've hit most all the options, you're probably asking
yourself, does ViaMAIL! allow you the ability to import and
AREAS.BBS file? You bet it does.
If you would like to import one now, you should export one from
WILDMAIL! or whatever tosser you're currently using and copy it
into the \VM10 directory. The from the 'Events' menu option, select
Internal Events and scroll down to an event called:
IMPORT-AREASBBS
Press enter on this event and it will display a screen of the
configuration options. Under DOS Path put the file filename and
path to your AREAS.BBS file - normally C:\VM10\AREAS.BBS and then
press F10 to save it. Press ESC one time to return to the 'Events'
menu and select Manually Run Event.
Highlight IMPORT-AREASBBS and press return. Say yes to the prompt
and ViaMAIL! will proceed to import the file. Basically rules to a
successfull importation are this.
1) Area MUST be in the Master list
2) If an WC area is already defined, the area tag name
will still be added, but as a passthru instead.
31) Tossing Mail. A program called ViaTOSS! has ben included that
performs the duties of mail tossing similar to WILDMAIL! and TIC
procssing similar to the way ViaTIC! has done for you in the past.
Since both of these function have been merged into one program, you
can activate them through the use of command line parameters.
Running ViaTOSS! at the DOS prompt by typing VT /? will present you
with a list of available command line parameters. Basically, they
have already been entered in the batch file created way back in
step #7. You should take a moment to go back at look at the
LINEx.BAT files and see the parameters and their usage.
32) Netmail Door. Included with ViaMAIL! is a door program to allow
your callers the ability to enter netmail messages from within
WILDCAT!. In the past you might have used a program like WCFIDO
that performed a similar function. ViaADDR! is much much more than
anything you've used in the past.
In the \VM10 directory, you'll find a file called FIDOENTR.BAT. You
should copy this file into your WILDCAT\BATCH\ directory and edit
it according to the directions inside the file. There really isn't
much to setting up this door.
Okay folks, please go easy on me now. I know this isn't much in the way
of docs, but it should give you enough familiarity to get you going.
Please PLEASE use the WSNET echo conference for your questions, but if
you really get stuck, give myself (Joe Martin) a call at 909-699-2215.
I'll try my best to fill in the gaps.
- EOF -
